https://linen.dev logo
Powered by
Invalid template directory with `rocket_dyn_templa...
# help
b
The erroneous log:
Copy code
2022-12-07T20:39:21.842672707Z ERROR rocket_dyn_templates::context: Invalid template directory 'templates': No such file or directory (os error 2).
2022-12-07T20:39:21.842680267Z ERROR _: Template initialization failed. Aborting launch.
The code works in a local run, but no when deploying. Is there a way to check the file system of the remote instance?
k
This is likely due to our lack of static file support, so this folder won't be included in the built deployment. Luckily this is something we are rolling out for our next release:
b
ok, so i’ll have to wait i guess 😅
so basically use static files with include_str?
what’s the project structure on the server?
isn’t it some kind of cargo project?
k
Yeah. Currently we use cargo package, so the static file folder won't be there after the project is built on the deployer. But support for this is coming in the next release which is coming soon
b
but i also tried to include every file using the include keyword in 
Cargo.toml
(at my templates got archived) ...
when can we expect for a version
k
Should be monday at the latest
b
ok great
s
This is great news. Looking forward to having a chance to play with this and make a thing with a user interface.
b
already updated?
k
Yeah, it is, we're a bit behind on the release notes but we'll post them in the morning
b
Ok great
Is there a way to force delete some deployments? They fail due to foreign key constraints (even though the project isn't using foreign keys, but another project does)
k
You mean the delete fails with FK error?
b
yes
if possible, you can also delete all my deployments & database from your side
k
Ah yes, I wasn't very clear when I responded to that last time, the error there is on our end. The 
delete
command should still succeed in stopping the deployment even though it gives you an FK error. It doesn't clean up your project 
target
however. We are working on a command to do this though which should be released soon as well
b
ok
wouldn't this be a problem if the rustc version is changed?
k
What exactly?
b
i currently get messages that crates are compiled for another rustc version
k
If you run 
cargo shuttle delete
in a project, it should stop the latest deployment. If you 
project rm
, your container for that project will be killed (but the name will stay reserved)
b
ah ok
k
Ah, yeah, we've seen this bug a few times before. Any specific crate?
b
hashbrown iirc
k
Yeah, that one we haven't figured out. Our deployers will build it with 1.59 IIRC, and we haven't found a way to make it not do that. It's near the top of our bug list, but it may be a while until we find a solution
b
ok
s
@broad-sundown-26978 btw, have you been able use the dyn templates with the new static folder resource?
k
Another btw, there is a work-around for the incompatible rust version bug now:
b
No, but because if some incompatible rust versions
Ok I'll check it out when I'm home in 2 weeks
k
You might not need the work-around in 2 weeks: 🤞 Have a good holiday!
b
Ok thanks 😅
3 Views
PreviousNext
Powered by